Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The Cisco ASA must be configured to restrict it from accepting outbound packets that contain an illegitimate address in the source address field via an egress filter or by enabling Unicast Reverse Path Forwarding (uRPF).
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-239871 | CASA-FW-000290 | SV-239871r665899_rule | Medium |
| Description |
|---|
| A compromised host in an enclave can be used by a malicious platform to launch cyberattacks on third parties. This is a common practice in "botnets", which are a collection of compromised computers using malware to attack other computers or networks. Denial-of-Service attacks frequently leverage IP source address spoofing to send packets to multiple hosts that, in turn, will then send return traffic to the hosts with the IP addresses that were forged. This can generate significant amounts of traffic. Therefore, protection measures to counteract IP source address spoofing must be taken. When uRPF is enabled in strict mode, the packet must be received on the interface that the device would use to forward the return packet, thereby mitigating IP source address spoofing. |
| STIG | Date |
|---|---|
| Cisco ASA Firewall Security Technical Implementation Guide | 2024-06-06 |
Details
| Check Text ( C-43104r665897_chk ) |
|---|
| Review the firewall configuration to verify uRPF or an egress filter has been configured on all internal interfaces to restrict the firewall from accepting outbound packets that contain an illegitimate address in the source address field. URF Example: ip verify reverse-path interface INSIDE ACL Example: Step 1: Verify that an ACL has been applied inbound on the inside interfaces as shown in the example below. access-group INSIDE_IN in interface INSIDE Step 2: Verify that the ACL only allows packets from legitimate internal source addresses. object-group network LAN_SUBNETS network-object 10.1.10.0 255.255.255.0 network-object 10.1.12.0 255.255.255.0 network-object 10.1.13.0 255.255.255.0 network-object 10.1.22.0 255.255.255.0 … … … access-list INSIDE_IN extended permit ip object-group LAN_SUBNETS any access-list INSIDE_IN extended deny ip any any Note: Traffic that is permitted must be in compliance with the PPSM. If uRPF or an egress ACL to restrict the firewall from accepting outbound IP packets that contain an illegitimate address in the source address field has not been configured on all internal interfaces, this is a finding. |
| Fix Text (F-43063r665898_fix) |
|---|
| Configure the firewall with an egress filter or uRPF on all internal interfaces to restrict the firewall from accepting any outbound packet that contains an illegitimate address in the source field. URF Example: ip verify reverse-path interface INSIDE ACL Example: Step 1: Configure an object group containing the allowed subnets as shown in the example below. ASA(config)# object-group network LAN_SUBNETS ASA(config-network-object-group)# network-object 10.1.10.0 255.255.255.0 ASA(config-network-object-group)# network-object 10.1.12.0 255.255.255.0 ASA(config-network-object-group)# network-object 10.1.13.0 255.255.255.0 ASA(config-network-object-group)# network-object 10.1.22.0 255.255.255.0 ASA(config-network-object-group)# exit Step 2: Configure the ACL. ASA(config)# access-list INSIDE_IN permit ip object-group LAN_SUBNETS any ASA(config)# access-list INSIDE_IN deny ip any any Note: Traffic that is permitted must be in compliance with the PPSM. Step 3: Apply the ACL inbound on the inside interface. ASA(config)# access-group INSIDE_IN in interface INSIDE |